Determining shortcut rules for bypassing waypoint network device(s)

ABSTRACT

Methods, computer program products, and systems are presented. The methods include, for instance: obtaining, by one or more processor, metadata of at least one packet of a network stream; and determining, by the one or more processor, a shortcut rule for the network stream to bypass at least one waypoint network, the shortcut rule being determined using the metadata of the at least one packet of the network stream. In one embodiment, the obtaining includes obtaining the metadata from the at least one waypoint network. In another embodiment, the obtaining comprises obtaining the metadata from multiple packets of the network stream, and the determining comprises using the metadata of the multiple packets of the network stream to determine the shortcut rule. In a further embodiment, the determining includes analyzing a header of the at least one packet of the network stream.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority of U.S. patentapplication Ser. No. 14/741,832 filed Jun. 17, 2015, entitled,“Determining Shortcut Rules for Bypassing Waypoint Network Device(s),”the entirety of which is hereby incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates to virtualization technologies, includingvirtual networking and virtual computing, and more particularly todetermining shortcut rules for bypassing waypoint network devices. Forexample, the waypoint networks can be waypoint networks of a servicechain.

BACKGROUND

Software defined networking and virtualization technologies allow, forexample, networking functions previously performed in a single networkdevice, such as a switch, router, firewall, or security device, to beseparated and virtualized for operation across a virtual network and/orover many virtual machines. For instance, these networking functions canbe separated and hosted on separate waypoint network devices which arevirtualized and located on separate computing nodes. Such aconfiguration allows for dynamically increasing or decreasing the amountof computing resources devoted to performing specific networkingfunctions in response to changing demand during ongoing operation. Bycontrast, traditional methods using specific fixed hardware devices,such as dedicated firewalls or dedicated address translation devices,can be inefficient, as some fixed devices may have excess capacity andother fixed devices may be fully utilized. Software defined networkingcan alleviate such a situation by allowing networking functions to runin virtual machines which can be launched in real-time to meet increaseddemand, rather than devoting fixed hardware to the networking functionsbased on out of date estimates.

In a software defined network infrastructure, network peers, clients, orservers, which may run on physical machines or virtual machines, cancommunicate by establishing a network stream or session. The networkstream, which includes numerous network packets, may pass throughnumerous network devices, such as the waypoint network devices describedabove, which can perform one or more networking functions on the networkstream. Depending on the desired networking functions, the networkstream can be configured to pass through one, two, three, or morewaypoint network devices, and each waypoint network device can performits networking function on the network packets of the network stream.For example, a network stream can pass sequentially through a firewallwaypoint network device, a load balancer waypoint network device, and anencryption waypoint network device.

However, in order for a network stream to pass through multiple waypointnetwork devices in overlay networks, the network stream may need to exitthe underlay physical network cloud, enter one waypoint network device,return to the underlay physical network cloud, enter another waypointnetwork device, return to the underlay physical network cloud again,etc. Each traversal between the network cloud and a waypoint networkdevice makes use of bandwidth and increases the latency delay of packetsof the network stream. Therefore, a need exists of technologicalsolution to improve the functioning of software defined networking, forexample, by optimizing bandwidth consumption of network streamstraversing waypoint network devices.

SUMMARY

Shortcomings of the prior art are overcome and additional advantages areprovided through the provision, in one aspect, of a method. The methodincludes, for instance, obtaining, by one or more processor, metadata ofat least one packet of a network stream. In addition, the methodincludes determining, by the one or more processor, a shortcut rule forthe network stream to bypass at least one waypoint network device.Further, the shortcut rule can be determined using the metadata of theat least one packet of the network stream. For example, the method canreduce consumption of network bandwidth and improve latency.

In one embodiment, the obtaining includes obtaining the metadata fromthe at least one waypoint network device. For example, once a waypointnetwork device decides to deny a stream of packets, the shortcut rulefor this network stream can be immediately determined and all packets inthis network stream can be dropped at the sending virtual switch tobypass all waypoint network devices.

In another embodiment, the obtaining includes, for instance, obtainingthe metadata from multiple packets of the network stream. In addition,the determining includes using the metadata of the multiple packets ofthe network stream to determine the shortcut rule. For example, themethod can use metadata after multiple packets of the network streamvisit waypoint network devices in a service chain in order to supportbypassing waypoint network devices that perform complex networkfunctions and require multiple packets to determine the policy orshortcut rule for the network stream.

In another embodiment, the determining includes analyzing a header ofthe at least one packet of the network stream. For example, the methodcan use address information located in the header to determine whether awaypoint network device can be bypassed.

In another aspect, a computer program product is provided. The computerprogram product includes a computer readable storage medium readable byone or more processor and storing instructions for execution by the oneor more processor for performing a method. The method includes, forinstance, obtaining, by one or more processor, metadata of at least onepacket of a network stream. In addition, the method includesdetermining, by the one or more processor, a shortcut rule for thenetwork stream to bypass at least one waypoint network device. Further,the shortcut rule may be determined using the metadata of the at leastone packet of the network stream. For example, the computer programproduct can reduce consumption of network bandwidth and improve latency.

In a further aspect, a system is provided. The system includes, forinstance a memory. In addition, the system includes one or moreprocessor in communication with the memory. Further, the system includesprogram instructions executable by the one or more processor via thememory to perform a method. The method includes, for instance,obtaining, by the one or more processor, metadata of at least one packetof a network stream. In addition, the method includes determining, bythe one or more processor, a shortcut rule for the network stream tobypass at least one waypoint network. Further, the shortcut rule isdetermined using the metadata of the at least one packet of the networkstream.

Additional features and advantages are realized through the techniquesset forth herein. Other embodiments and aspects are described in detailherein and are considered a part of the claimed invention.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more aspects of the present disclosure are particularly pointedout and distinctly claimed as examples in the claims at the conclusionof the specification. The foregoing and other objects, features, andadvantages of the present disclosure are apparent from the followingdetailed description taken in conjunction with the accompanying drawingsin which:

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention;

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention;

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention;

FIG. 4 depicts a hardware overview of a computing node, in accordancewith one or more aspects set forth herein;

FIG. 5 is an exemplary block diagram of a system, in accordance with oneor more aspects set forth herein;

FIG. 6 depicts embodiments of processes for determining shortcut rules,in accordance with one or more aspects set forth herein; and

FIG. 7 is a diagram illustrating further aspects of processes fordetermining shortcut rules, in accordance with one or more aspects setforth herein.

DETAILED DESCRIPTION

Aspects of the present disclosure and certain features, advantages, anddetails thereof, are explained more fully below with reference to thenon-limiting examples illustrated in the accompanying drawings.Descriptions of well-known materials, fabrication tools, processingtechniques, etc., are omitted so as not to unnecessarily obscure thedisclosure in detail. It should be understood, however, that thedetailed description and the specific examples, while indicating aspectsof the invention, are given by way of illustration only, and not by wayof limitation. Various substitutions, modifications, additions, and/orarrangements, within the spirit and/or scope of the underlying inventiveconcepts will be apparent to those skilled in the art from thisdisclosure.

The present disclosure provides, in part, methods, computer programs,computer systems, network devices, and network policy devices fordetermining shortcut rules for bypassing waypoint network devices.Demand continues for software defined networking technologies, which canallow the separation of previously linked networking functions intoseparate computing units. These separate networking functions can beperformed on separate waypoint network devices located on separatewaypoint networks.

In certain cases, some of the network functions can be accomplished by awaypoint network device examining a relatively small number of networkpackets of the network stream during an initial period of time. Forinstance, a simple firewall rule to admit or deny a network sessionbased on source and destination internet protocol (IP) addresses andapplication protocol could perform its function after only a singlepacket of the network stream has been examined by a waypoint networkdevice performing a firewall networking function. In another example,the waypoint network device may be able to complete its network functionafter inspecting several network packets of the network stream. Ineither such example, although the waypoint network device may havecompleted its network function, the network stream will continue totraverse trough the waypoint network device on the waypoint network,needlessly using network bandwidth.

Advantageously, the present disclosure allows, for example, bypassing awaypoint network after a waypoint network device located therein hasfinished performing a networking function on a network stream. Thus, thepresent technique allows for the advantages of software definednetworking, such as separation and virtualization of network functions,without sacrificing bandwidth and latency.

Reference is made below to the drawings, which are not drawn to scalefor ease of understanding, wherein the same reference numbers usedthroughout different figures designate the same or similar components.

FIGS. 1-4 depict various aspects of computing, including cloudcomputing, in accordance with one or more aspects set forth herein.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and determining shortcut rules for bypassingwaypoint network devices 96 as described herein.

FIG. 4 depicts a hardware overview of a computing node 10, which may bea cloud computing node, a network device 120, 120-S, 120-D, 120-A, 120-B(FIG. 5), a network policy device 125 (FIG. 5), and/or a computing node130 (FIG. 5), in accordance with one or more aspects set forth herein.

Program/utility 40 as set forth in FIG. 1 can include one or moreprogram 440 as set forth in FIG. 4, and program/utility 40 as set forthin FIG. 1 can optionally include some or all of one or more program 441,442, 443, 444, 445.

One or more program 440 can have a set (at least one) of programmodules, and may be stored in memory 28 by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystem, one or more application programs, other program modules, programdata, and one or more program, or some combination thereof, may includean implementation of a networking environment. One or more program 440(and optionally at least one of one or more program 441, 442, 443, 444,445) generally carry out the functions and/or methodologies ofembodiments of the invention as described herein.

Referring again to FIG. 4:

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

FIG. 5 is an exemplary block diagram of a system 100, in accordance withone or more aspects set forth herein. In the embodiment of FIG. 5,system 100 includes numerous networks 110, 110-S, 110-D, 110-A, 110-B,which may be physical networks or virtual networks. A physical networkcan be, for example, a physical telecommunications network connectingnumerous computer nodes or systems, such as computer servers andcomputer clients. By contrast a virtual network can, for example,combine numerous physical networks or parts thereof into a logicalvirtual network. In another example, numerous virtual networks can bedefined over a single physical network.

By way of explanation, FIG. 5 depicts an example environment in which asource network 110-S is connected to a destination network 110-D througha network cloud. In some of the examples to follow, a network stream maybe established between source network 110-S and destination network110-D. Waypoint network 110-A and waypoint network 110-B may be used toperform desired networking functions.

In one embodiment, a network, e.g., a network 110, 110-S, 110-D, 110-A,110-B, connects to one or more network devices, e.g., network devices120, 120-S, 120-D, 120-A, 120-B, and one or more computing nodes, e.g.,computing nodes 130. For example, network device 120 can be a networkedge device, such as a network switch or network router, and can operateat one or more network protocol layers, such as layer 2 (L2), layer 3(L3), or layers 4-7 (L4-L7). In another example, network device 120 cancombine the features of network switches and network routers. Ingeneral, each of network device 120 and computing node 130 can be orinclude a computing node 10 (FIG. 4), details of which are describedbelow.

In one embodiment, a network policy device 125 can be included, so thatcontrol plane information between network devices 120 may becommunicated. In one example, network policy device 125 can be one ofthe network devices 120 provisioned with software to perform thefunctions noted below with respect to network policy device 125. In theembodiment of FIG. 5, network policy device 125 is shown as a separatedevice.

It should be understood that to most clearly explain the presenttechniques, networks 110, 110-S, 110-D, 110-A, 110-B are described andreferred to as networks. In practice, the networks are embodied byphysical machines that can be or include computing nodes as describedherein, and can host multiple virtual machines and waypoints. In someexamples, a network can include one physical machine, and in otherexamples, a network can include more than one physical machine.

In one embodiment, computing nodes 130 can each have one or more virtualmachines, e.g., virtual machines VM-S, VM-D. For example, a virtualmachine VM-S is a software computer that can run an operating system andapplications, and can have access to virtual devices. In addition, avirtual machine can span more than one physical machine, and numerousvirtual machines can exist on the same set of physical machines. Fromthe standpoint of a client, such as another virtual machine or physicalmachine, communication and interaction with a virtual machine proceedsjust as with physical machines. Continuing with reference to theembodiment of FIG. 5, a virtual machine VM-S can establish communicationwith a virtual machine VM-D. For example, virtual machine VM-S can belocated on network 110-S and virtual machine VM-D can be located onnetwork 110-D. In addition, physical communication can take place usingvirtual overlay network devices 120-S, 120-D, logically on top ofunderlying physical network devices 120.

By way of example, a network stream can be established between virtualmachine VM-S on source network 110-S and virtual machine VM-D ondestination network 110-D. In such a case, the network stream maytraverse waypoint network 110-A, and computing node 130 of waypointnetwork 110-A may be provisioned with a virtual machine for performing anetwork function on the network stream. Similarly, the network streammay next traverse waypoint network 110-B, and computing node 130 ofwaypoint network 110-B may be provisioned with a virtual machine forperforming a network function on the network stream. Details of suchinteractions will be provided below with respect to FIG. 7.

FIG. 6 depicts embodiments of processes for updating networks, inaccordance with one or more aspects set forth herein. By way of example,the processes described with respect to FIG. 6 can be performed usingone or more program 440 on one or more network policy device 125 (FIG.5), as detailed with respect to FIG. 4.

In the embodiment of FIG. 6, one or more program 440 at block 713obtains metadata of at least one packet of a network stream; and one ormore program 440 at block 715 determines a shortcut rule for the networkstream to bypass at least one waypoint network device, the shortcut rulebeing determined using the metadata of the at least one packet of thenetwork stream.

For instance, the waypoint network device can be a waypoint networkdevice along a service chain, and the shortcut rule can be determinedafter the packet visits waypoint network devices along the servicechain. In addition, metadata can be or include a formatted serviceheader to be placed after an IP header. In such a case, the metadata canbe exchanged between network policy devices and virtual switches orwaypoint network devices, and can gather necessary information alongwaypoint network devices when packets traverse through the servicechain.

In one embodiment, the first virtual switch which is closest to thesending virtual machine sends the packet header to network policydevice, which creates a footprint rule for the stream and returns packetmetadata to the first virtual switch. In addition, the first virtualswitch receives the metadata, inserts it into the packet, and sends thepacket to a virtual switch connecting to the waypoint. Further, thewaypoint receives the packet, and if possible, can determine actions totake on the stream, and updates the actions into the metadata and sendsthe updated metadata to the network policy device. Next, the waypointreturns the packet to the virtual switch and the virtual switchcontinues subsequent forwarding.

In response to the network policy device receiving the updated metadatafrom waypoint, the network policy device will find out the footprintrule of the stream by stream ID in the metadata, and then update thefootprint rule with the actions carried in the metadata. If the metadatais reported from the last waypoint along a service chain, the footprintrule will be claimed as the final shortcut rule. For example, thenetwork policy device pushes the final shortcut rule to the firstvirtual switch.

In one embodiment, one or more program 440 at block 713 obtains themetadata from the at least one waypoint network device.

In one embodiment, one or more program 440 at block 713 obtains themetadata from multiple packets of the network stream, and one or moreprogram 440 at block 715 determines a shortcut rule by using themetadata of the multiple packets of the network stream to determine theshortcut rule.

For instance, metadata can be stateful for a packet, but statelessbetween different packets in a stream. For example, stateful metadatacan mean that for the same packet, the metadata is updated when visitingeach waypoint network device. In contrast, stateless metadata can meanthat metadata of a prior packet will not be used by a subsequent packetof the network stream. Therefore metadata of multiple packets of anetwork stream can include first metadata of a first packet, secondmetadata of a second packet, and so forth.

In one embodiment, one or more program 440 at block 715 determines ashortcut rule by analyzing a header of the at least one packet of thenetwork stream.

In one embodiment, one or more program 440 at block 713 obtains themetadata from the at least one waypoint network device, where themetadata includes deep packet inspection information of the at least onepacket of the network stream.

In one embodiment, one or more program 440 at block 713 obtains themetadata from a firewall device of the at least one waypoint networkdevice, and one or more program 440 at block 715 determines a shortcutrule that includes instructions for the network stream to bypass thefirewall device of the at least one waypoint network device.

In one embodiment, one or more program 440 at block 713 obtains themetadata from a load balancer device of the at least one waypointnetwork device, and one or more program 440 at block 715 determines ashortcut rule that includes instructions for the network stream tobypass the load balancer device of the at least one waypoint networkdevice.

In one embodiment, one or more program 440 at block 713 obtains themetadata from multiple waypoint network devices and one or more program440 at block 715 determines a shortcut rule that includes instructionsfor the network stream to bypass the multiple waypoint network devices.

In one embodiment, one or more program 440 at block 715 determines ashortcut rule that includes instructions for the network stream tobypass one waypoint network device of the at least one waypoint networkdevice and traverse another waypoint network device of the at least onewaypoint network device.

In one embodiment, one or more program 440 at block 713 obtains themetadata from a source network of the network stream.

In one embodiment, one or more program 440 at block 715 determines ashortcut rule that includes instructions for a source network of thenetwork stream to bypass the at least one waypoint network device androute the network stream directly to a destination network.

In one embodiment, one or more program 440 at block 713 obtains themetadata indicating that a firewall has allowed the network stream basedon the source and destination addresses and protocols.

In one embodiment, one or more program 440 at block 713 obtains themetadata indicating that a load balancer system has determined whichdestination virtual machine to connect the source virtual machine to,and that such determination is final for that network stream, and thereis no longer any need for the load balancer to service the networkstream.

In one embodiment, one or more program 440 at block 713 obtains themetadata by receiving information that indicates that a networkintrusion detection or prevention system has analyzed one or morenetwork packets of the network stream, and determined that the networkstream may be considered safe to pass through the network.

In one embodiment, metadata is a formatted service header placed afterthe IP header of a network packet. In such a case, the metadata can beexchanged between network policy devices and virtual switches orwaypoint network devices, and can include necessary information gatheredalong waypoint network devices as the network packet traverses throughthe service chain. For example, metadata can be used to collectnecessary information from all waypoints in a service chain. Inaddition, if a waypoint network device decides to deny a stream ofpackets, such a deterministic action can immediately be derived, andthere would be no need for the network packet to traverse subsequentwaypoints, which could be bypassed using the present technique.

In one embodiment, metadata can be stateful for a packet, but statelessbetween different packets in a stream. For example, stateful metadatacan mean that for the same packet, the metadata is updated when visitingeach waypoint network device. In contrast, stateless metadata can meanthat metadata of a prior packet will not be used by a subsequent packetof the network stream.

In one embodiment, one packet of a network stream may be enough todetermine the shortcut rule, and in another embodiment multiple packetsof a network stream may be needed to determine the shortcut rule.

In one embodiment, one or more program 440 at block 713 obtains themetadata indicating that a waypoint device has performed deep packetinspection of multiple packets of the network stream in order to findout that a higher level application protocol, such as a businessdatabase application, is permitted to communicate between a sourcevirtual machine and a destination virtual machine.

In one embodiment, one or more program 440 at block 713 obtains themetadata showing that one or more previously created shortcut rulesshould either be updated or terminated.

In one embodiment, one or more program 440 at block 715 determines ashortcut rule that includes a time limit for the shortcut rule to beoperational, so that after the time limit, the shortcut rule is deleted.

In one embodiment, one or more program 440 at block 715 determines ashortcut rule by determining which waypoint network devices may bebypassed and which waypoint network devices may not be bypassed, and forexample the shortcut rule can specify that an encryption waypoint is notto be bypassed because the networking function of encryption is desiredto be always operational on the network stream.

In one embodiment, one or more program 440 at block 715 determines ashortcut rule that reduces network bandwidth used by the network streamif network bandwidth is needed.

In one embodiment, one or more program 440 at block 715 determines ashortcut rule that decreases end to end latency of the network stream,if the network stream requires a decrease in end to end latency.

In one embodiment, metadata can include a header information as depictedin Table A.

TABLE A Example Metadata Header Format Field Summary Service ChainUniquely identifies a particular service chain. Identifier (SCID)Service Index Initially indicates the number of waypoints along aservice chain, and can be decremented by each waypoint. Stream Uniquelyidentifies a particular network stream Identifier Action Set A varyingnumber of type-length-value (TLV) elements indicating action decisioninformation for the stream

In different embodiments, the different blocks of one or more program440 can run on the same or different set of processor(s), which can belocated on various physical and/or virtual machines. For example, afirst block can run on one processor, and a second block can run on adifferent processor.

FIG. 7 is a diagram illustrating further aspects of processes forupdating networks, in accordance with one or more aspects set forthherein.

FIG. 7 may be used to understand certain details of the presentdisclosure when a network stream traverses numerous waypoint networks,and will explain how the techniques disclosed herein may be used toovercome such problems by allowing selective bypassing of waypointnetwork devices subsequent to successful completion of their dedicatednetwork functions. As will be explained below, the techniques disclosedherein will allow for elimination of one or more hops from a networkcloud to a waypoint network, as shortcut rules are created, updated, andimplemented. In such a case, the benefits of software definednetworking, allowing virtualization of the performed networkingfunctions, may be reaped, while mitigating the downside of additionalnetwork hops and concomitant bandwidth usage and incremental latency

By way of explanation, in FIG. 7, processes are illustrated from thepoint of view of a network policy device one or more program 440, asource network one or more program 441, waypoint network one or moreprogram 442, and a destination network one or more program 444. In oneembodiment, one or more program 440 runs on one or more processor 16(FIG. 4) of a network policy device 125 (FIG. 5). In one embodiment, oneor more program 441 runs on one or more processor 16 (FIG. 4) of asource edge network device 120-S (FIG. 5). In one embodiment, one ormore program 442 runs on one or more processor 16 (FIG. 4) of a waypointnetwork device 120-A (FIG. 5). In one embodiment, one or more program444 runs on one or more processor 16 (FIG. 4) of a destination edgenetwork device 120-D (FIG. 5). In other embodiments, various programscan run on a different complement of devices. For example, in oneembodiment, one or more program 440 and one or more program 441 can bothrun on source edge network device 120-S (FIG. 5), which cansimultaneously service the source network and provide network policydevice functions for the entire network. Such a configuration may bedesirable to eliminate the deployment of a dedicated network policydevice.

FIG. 7 illustrates a network stream having multiple network packetsbeing communicated between a virtual machine VM-S located on a sourcenetwork and a virtual machine VM-D located on a destination network, anddescribes an example of determining a shortcut rule for a network streamto bypass a single waypoint network device using metadata. Inparticular, in one example, the network stream is from IP address andport VM_S_IP_1 on virtual machine VM-S to IP address and port VM_D_IP_1on virtual machine VM-D, with application protocol P1 (VM_S_IP_1,VM_D_IP_1, and P1 are variables that contain the correspondinginformation).

In the embodiment of FIG. 7, one or more program 441 (e.g., running on asource edge network device 120-S of FIG. 5) at block 701 receives apacket of a network stream from virtual machine VM-S.

In one embodiment, one or more program 441 at block 702 checks to see ifa shortcut rule corresponds to the network stream. Next, one or moreprogram 441 at block 703 sends metadata of the network packet to anetwork policy device (e.g., network policy device 125 of FIG. 5) if ashortcut rule corresponding to the network stream does not exist.

In one embodiment, one or more program 440 (e.g., running on networkpolicy device 125 of FIG. 5) at block 704 obtains the metadata of atleast one network packet of the network stream, for example, byreceiving it from the source network. Next, one or more program 440 atblock 705 updates the metadata of the network packet and creates afootprint rule to keep track of the network stream. For instance, thefootprint rule can include the internet protocol 5-tuple of the networkstream, which includes the source IP address, source IP port,destination IP address, destination IP port, and the applicationprotocol.

In one embodiment, one or more program 441 at block 706 receives theupdated metadata. Next, one or more program 441 at block 707 sends thenetwork packet of the network stream, after replacing the header withinformation derived from the updated metadata, to the waypoint A network110-A (FIG. 5).

In one embodiment, one or more program 442 (e.g., running on waypointnetwork device 120-A and/or waypoint computing node 130 of FIG. 5) atblock 708 receives the network packet of the network stream. Next, oneor more program 442 at block 709 performs a networking function A on thenetwork packet of the network stream.

In one example, one or more program 442 at block 709 performs a firewallnetworking function of admission control, determining whether thenetwork stream should be allowed to reach the destination network.

In one example, one or more program 442 at block 709 performs a loadbalancing networking function by distributing various network streams todifferent destination virtual machines located throughout the network.

In one example, one or more program 442 at block 709 performs anetworking function of network intrusion detection and/or provision byperforming deep packet inspection of numerous packets of the networkstream.

In one example, one or more program 442 at block 709 performs anetworking function of encrypting network data to ensure networksecurity.

In one embodiment, one or more program 442 at block 710 sends metadataof the network packet to a network policy device. Next, one or moreprogram 442 at block 711 sends the network packet of the network streamto the destination network 110-D (FIG. 5). In one embodiment, one ormore program 444 (e.g., running on destination network device 120-D) atblock 712 receives the network packet of the network stream.

In one embodiment, one or more program 440 at block 713 obtains metadataof at least another network packet of the network stream, for example,by receiving it from the waypoint A network (e.g., after one or moreprogram 442 at block 710 sent the metadata). Next, one or more program440 at block 714 recognizes that the network stream of the networkpacket matches the footprint rule previously created at block 704. Next,one or more program 440 at block 715 determines a shortcut rule for thenetwork stream to bypass waypoint network device 120-A (FIG. 5). In suchan example, the shortcut rule is determined using the metadata of the atleast another packet of the network stream.

In addition, one or more program 440 at block 715 sends the shortcutrule to the source network. In one embodiment, one or more program 441at block 716 receives the shortcut rule from the network policy device.

In one embodiment, after the process described above, the followingshortcut table is established:

TABLE B Shortcut Table Source Destination Network Device Address AddressProtocol Shortcut Network device VM_S_IP_1 VM_D_IP_1 P1 Network 120-S110-D

By way of explanation, in the shortcut table above, the columns indicatethe network device to apply the shortcut rule, the network stream sourceaddress (e.g., IP address and port), the network stream destinationaddress (e.g., IP address and port), the network stream protocol, andthe shortcut. In the example given, the shortcut table includes ashortcut rule, to be implemented by the source network device 120-S, forthe network stream to bypass waypoint network device 120-A (FIG. 5) andbe routed directly to network 110-D (FIG. 5). In a fully deployedsystem, hundreds, thousands, or millions of entries may be present inthe shortcut table. For example, the shortcut table can be stored by oneor more processor 40 within network policy device 125 (FIG. 5). In oneembodiment, the entire shortcut table can be sent to each network devicein the software defined network infrastructure. In another embodiment,only relevant portions of the shortcut table may be sent to each networkdevice to minimize overhead.

In one embodiment, since a shortcut rule has been established, the nextnetwork packet of the network stream can be used to illustrate thefunctioning of the technique described herein.

Once again, in one embodiment, one or more program 441 at block 701receives a packet of a network stream from virtual machine VM-S. Next,one or more program 441 at block 702 checks to see if a shortcut rulecorresponds to the network stream, and finds the shortcut rule. Next,one or more program 441 at block 717 sends the network packet of thenetwork stream directly to the destination network 110-D (FIG. 5). Inone embodiment, one or more program 444 at block 712 receives thenetwork packet of the network stream. Advantageously, this andsubsequent network packets of the network stream may bypass waypointnetwork device 120-A.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used herein, thesingular forms “a,” “an,” and “the” are intended to include the pluralforms as well, unless the context clearly indicates otherwise. It willbe further understood that the terms “comprise” (and any form ofcomprise, such as “comprises” and “comprising”), “have” (and any form ofhave, such as “has” and “having”), “include” (and any form of include,such as “includes” and “including”), and “contain” (and any form ofcontain, such as “contains” and “containing”) are open-ended linkingverbs. As a result, a method or device that “comprises,” “has,”“includes,” or “contains” one or more steps or elements possesses thoseone or more steps or elements, but is not limited to possessing onlythose one or more steps or elements. Likewise, a step of a method or anelement of a device that “comprises,” “has,” “includes,” or “contains”one or more features possesses those one or more features, but is notlimited to possessing only those one or more features. Furthermore, adevice or structure that is configured in a certain way is configured inat least that way, but may also be configured in ways that are notlisted.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below, if any, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description set forth herein has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited to the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the disclosure. Theembodiment was chosen and described in order to best explain theprinciples of one or more aspects set forth herein and the practicalapplication, and to enable others of ordinary skill in the art tounderstand one or more aspects as described herein for variousembodiments with various modifications as are suited to the particularuse contemplated.

What is claimed is:
 1. A method comprising: obtaining, by one or moreprocessor, metadata of at least one packet of a network stream; anddetermining, by the one or more processor, a shortcut rule for thenetwork stream to bypass at least one waypoint network, the shortcutrule being determined using the metadata of the at least one packet ofthe network stream, wherein the determined shortcut rule includesinstructions for a source network of the network stream to bypass the atleast one waypoint network and wherein the method includes extractingthe metadata from a formatted service header of the at least one packetof the network stream, wherein the formatted service header includes themetadata placed after an IP address of the at least one network stream,and wherein the extracted metadata includes a service chain identifier(SCID) that uniquely identifies a particular service chain.
 2. Themethod of claim 1, wherein the obtaining comprises obtaining themetadata from the at least one waypoint network.
 3. The method of claim1, wherein the obtaining comprises obtaining the metadata from multiplepackets of the network stream, and the determining comprises using themetadata of the multiple packets of the network stream to determine theshortcut rule.
 4. The method of claim 1, wherein the obtaining includesobtaining the metadata from the at least one waypoint network, whereinthe metadata includes deep packet inspection information of the at leastone packet of the network stream.
 5. The method of claim 1, wherein theobtaining includes obtaining the metadata from a firewall device of theat least one waypoint network, and the determined shortcut rule includesinstructions for the network stream to bypass the firewall device of theat least one waypoint network.
 6. The method of claim 1, wherein theobtaining includes obtaining the metadata from a load balancer device ofthe at least one waypoint network, and the determined shortcut ruleincludes instructions for the network stream to bypass the load balancerdevice of the at least one waypoint network.
 7. The method of claim 1,wherein the obtaining includes obtaining the metadata from multiplewaypoint networks, and the determined shortcut rule includesinstructions for the network stream to bypass the multiple waypointnetworks.
 8. The method of claim 1, wherein the obtaining comprisesobtaining the metadata from a source network of the network stream. 9.The method of claim 1, wherein the determined shortcut rule includesinstructions for a source network of the network stream to bypass the atleast one waypoint network and route the network stream directly to adestination network.
 10. A computer program product comprising: acomputer readable storage medium readable by one or more processingcircuit and storing instructions for execution by one or more processorfor performing a method comprising: obtaining metadata of at least onepacket of a network stream; determining a shortcut rule for the networkstream to bypass at least one waypoint network, the shortcut rule beingdetermined using the metadata of the at least one packet of the networkstream, wherein the determined shortcut rule includes instructions for asource network of the network stream to bypass the at least one waypointnetwork and wherein the method includes extracting the metadata from aformatted service header of the at least one packet of the networkstream, wherein the formatted service header includes the metadataplaced after an IP address of the at least one network stream, andwherein the extracted metadata includes a service chain identifier(SCID) that uniquely identifies a particular service chain.
 11. A systemcomprising: a memory; one or more processor in communication with thememory; and program instructions executable by the one or more processorvia the memory to perform a method, the method comprising: obtainingmetadata of at least one packet of a network stream; and determining ashortcut rule for the network stream to bypass at least one waypointnetwork, the shortcut rule being determined using the metadata of the atleast one packet of the network stream, wherein the determined shortcutrule includes instructions for a source network of the network stream tobypass the at least one waypoint network and wherein the method includesextracting the metadata from a formatted service header of the at leastone packet of the network stream, wherein the formatted service headerincludes the metadata placed after an IP address of the at least onenetwork stream, and wherein the extracted metadata includes a servicechain identifier (SCID) that uniquely identifies a particular servicechain.
 12. The system of claim 11, wherein the determined shortcut ruleis a rule for performance by a source network, wherein the sourcenetwork by performance of the shortcut rule, bypasses the waypointnetwork by sending the network stream directly to a destination network.13. The system of claim 11, wherein the determined shortcut rule is arule that reduces network bandwidth used by the network stream.
 14. Thesystem of claim 11, wherein the determined shortcut rule is a rule thatdecreases end to end latency of the network stream.
 15. The system ofclaim 11, wherein the determined shortcut rule is a rule that includes atime limit for the shortcut rule to be operational.
 16. The system ofclaim 11, wherein the metadata of the at least one packet of the networkstream is extracted from a formatted service header of the at least onenetwork stream, wherein the formatted service header includes themetadata placed after an IP address of the at least one network stream.17. The system of claim 11, wherein the obtaining includes obtaining themetadata from a computing node that transmits the network stream,wherein the computing node sends the metadata for performance of theobtaining in response to a determining by the computing node that thereis no shortcut rule active for the network stream.
 18. The system ofclaim 11, wherein the obtaining includes obtaining the metadata from acomputing node that transmits the network stream to a waypoint device,and wherein the method includes sending to the computing node updateddata for use by the computing node for replacing a header of atransmitted packet of the network stream based on the updated data, thetransmitted packet being transmitted by the computing node to a waypointdevice.
 19. The system of claim 11, wherein the obtaining includesobtaining the metadata from a computing node that transmits the networkstream to a waypoint device, wherein the method includes sending to thecomputing node updated data and wherein the method includes receivingfrom the waypoint device second metadata that is changed from themetadata based on the updated data, wherein the determining the shortcutrule includes using the metadata and the second metadata.
 20. The systemof claim 11, wherein the obtaining includes obtaining the metadata froma computing node that transmits the network stream to a second computingnode, wherein the method includes receiving from the second computingnode second metadata, wherein the determining the shortcut rule includesusing the metadata and the second metadata.